Dynamic read based on read statistics

ABSTRACT

Apparatuses, systems, and methods are disclosed for dynamic read operations. A controller monitors one or more read statistics during a read operation for data of a non-volatile memory die. The controller determines whether one or more read statistics satisfy a threshold for a read operation. The controller dynamically modifies a read operation based on determining that one or more read statistics fail to satisfy a threshold.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent Application No. 62/752,747 filed Oct. 30, 2018 entitled “DYNAMIC READ BASED ON READ STATISTICS”, incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present disclosure, in various embodiments, relates to reading data from non-volatile memory and more particularly relates to dynamic read operations based on read statistics.

BACKGROUND

A non-volatile memory device controller or driver may encode or transform data to be written to a non-volatile medium. Data may be encoded or transformed in a variety of ways, such as by compressing the data, encrypting the data, scrambling or whitening the data (so that an approximately equal number of binary zeros and ones are stored), applying an error correcting code to the data, or the like.

When a read operation is performed for the non-volatile medium, errors may be present in the data. Errors may arise due to various phenomena that affect the stored data, such as charge leakage, disturbances from programming or erasing data in nearby regions of the non-volatile medium, temperature effects, or the like. Errors may also occur as data is moved during read, write, or garbage collection operations.

When the driver or controller decodes the data, or reverses the data transformation, errors may increase the amount of time or power used by the decoder. For example, if a parity check fails for an error correcting code, it may take further time and power to detect and correct the errors before the decoded data can be retrieved. A high error rate may also prevent the decoder from decoding the data, or reversing the data transformation. For example, a decoder for an error-correcting code may fail, and issue an error message indicating that an uncorrectable error has occurred.

SUMMARY

Apparatuses are presented for dynamic read operations. In one embodiment, an apparatus includes an on-die controller for a non-volatile memory die. In a certain embodiment, an on-die controller is configured to monitor one or more read statistics during a read operation for data of a non-volatile memory die. In a further embodiment, an on-die controller is configured to determine whether one or more read statistics satisfy a threshold for a read operation. In certain embodiments, an on-die controller is configured to dynamically modify a read operation based on determining that one or more read statistics fail to satisfy a threshold.

Methods are presented for dynamic read operations. In one embodiment, a method includes initiating a read operation for data of a non-volatile memory element. In a further embodiment, data may be stored subject to a data transformation that balances bit values for the data. In a certain embodiment, a method includes tracking an ongoing balance between bit values for data during a read operation. In a further embodiment, a method includes dynamically adjusting a read operation based on a tracked ongoing balance between bit values.

An apparatus, in another embodiment, includes means for monitoring one or more read statistics during a read operation for data of a non-volatile memory die. In a certain embodiment, an apparatus includes means for comparing one or more read statistics to one or more expected statistics for data. In a further embodiment, an apparatus includes means for dynamically updating a read operation based on a variance between one or more read statistics and one or more expected statistics for data.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description is included below with reference to specific embodiments illustrated in the appended drawings. Understanding that these drawings depict only certain embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the disclosure is described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

FIG. 1 is a schematic block diagram of one embodiment of a system comprising a dynamic read component;

FIG. 2 is a schematic block diagram illustrating another embodiment of a system comprising a dynamic read component;

FIG. 3A is a graph illustrating one embodiment of a distribution of threshold voltages for cells of a non-volatile memory element;

FIG. 3B is a graph illustrating another embodiment of a distribution of threshold voltages for cells of a non-volatile memory element;

FIG. 3C is a graph illustrating a further embodiment of a distribution of threshold voltages for cells of a non-volatile memory element;

FIG. 3D is a graph illustrating another embodiment of a distribution of threshold voltages for cells of a non-volatile memory element;

FIG. 4 is a schematic block diagram illustrating one embodiment of an internal read size in relation to a data transfer size;

FIG. 5 is a schematic block diagram illustrating one embodiment of a dynamic read component;

FIG. 6 is a schematic block diagram illustrating another embodiment of a dynamic read component;

FIG. 7 is a schematic flow chart diagram illustrating one embodiment of a method for a dynamic read operation based on read statistics; and

FIG. 8 is a schematic flow chart diagram illustrating a further embodiment of a method for a dynamic read operation based on read statistics.

FIG. 9 is a conceptual block diagram showing an application-specific integrated circuit (ASIC) for performing dynamic read, according to at least one embodiment of the invention.

FIG. 10 illustrates a flowchart representation of a method for DMC ECC using recalibrated thresholds in certain scenarios, in accordance with some embodiments.

FIG. 11 illustrates a flowchart representation of a method for DMC ECC using data block header information, in accordance with some embodiments.

FIG. 12 illustrates a flowchart representation of a method for DMC ECC using data block header information, in accordance with some embodiments.

FIG. 13 illustrates a flowchart representation of a method for DMC ECC in accordance with some embodiments.

DETAILED DESCRIPTION

Aspects of the present disclosure may be embodied as an apparatus, system, method, or computer program product. Accordingly, aspects of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, or the like) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module,” “apparatus,” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more non-transitory computer readable storage media storing computer readable and/or executable program code.

Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.

Modules may also be implemented at least partially in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a module of executable code may include a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, across several memory devices, or the like. Where a module or portions of a module are implemented in software, the software portions may be stored on one or more computer readable and/or executable storage media. Any combination of one or more computer readable storage media may be utilized. A computer readable storage medium may include, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing, but would not include propagating signals. In the context of this document, a computer readable and/or executable storage medium may be any tangible and/or non-transitory medium that may contain or store a program for use by or in connection with an instruction execution system, apparatus, processor, or device.

Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Python, Java, Smalltalk, C++, C#, Objective C, or the like, conventional procedural programming languages, such as the “C” programming language, scripting programming languages, and/or other similar programming languages. The program code may execute partly or entirely on one or more of a user's computer and/or on a remote computer or server over a data network or the like.

A component, as used herein, comprises a tangible, physical, non-transitory device. For example, a component may be implemented as a hardware logic circuit comprising custom VLSI circuits, gate arrays, or other integrated circuits; off-the-shelf semiconductors such as logic chips, transistors, or other discrete devices; and/or other mechanical or electrical devices. A component may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. A component may comprise one or more silicon integrated circuit devices (e.g., chips, die, die planes, packages) or other discrete electrical devices, in electrical communication with one or more other components through electrical lines of a printed circuit board (PCB) or the like. Each of the modules described herein, in certain embodiments, may alternatively be embodied by or implemented as a component.

A circuit, as used herein, comprises a set of one or more electrical and/or electronic components providing one or more pathways for electrical current. In certain embodiments, a circuit may include a return pathway for electrical current, so that the circuit is a closed loop. In another embodiment, however, a set of components that does not include a return pathway for electrical current may be referred to as a circuit (e.g., an open loop). For example, an integrated circuit may be referred to as a circuit regardless of whether the integrated circuit is coupled to ground (as a return pathway for electrical current) or not. In various embodiments, a circuit may include a portion of an integrated circuit, an integrated circuit, a set of integrated circuits, a set of non-integrated electrical and/or electrical components with or without integrated circuit devices, or the like. In one embodiment, a circuit may include custom VLSI circuits, gate arrays, logic circuits, or other integrated circuits; off-the-shelf semiconductors such as logic chips, transistors, or other discrete devices; and/or other mechanical or electrical devices. A circuit may also be implemented as a synthesized circuit in a programmable hardware device such as field programmable gate array, programmable array logic, programmable logic device, or the like (e.g., as firmware, a netlist, or the like). A circuit may comprise one or more silicon integrated circuit devices (e.g., chips, die, die planes, packages) or other discrete electrical devices, in electrical communication with one or more other components through electrical lines of a printed circuit board (PCB) or the like. Each of the modules described herein, in certain embodiments, may be embodied by or implemented as a circuit.

Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive and/or mutually inclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

Aspects of the present disclosure are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of the disclosure. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a computer or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor or other programmable data processing apparatus, create means for implementing the functions and/or acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

It should also be noted that, m some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated figures. Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment.

In the following detailed description, reference is made to the accompanying drawings, which form a part thereof. The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description. The description of elements in each figure may refer to elements of proceeding figures. Like numbers may refer to like elements in the figures, including alternate embodiments of like elements.

FIG. 1 is a block diagram of one embodiment of a system 100 comprising one or more dynamic read components 150 for a non-volatile memory device 120. A dynamic read component 150 may be part of a non-volatile memory element 123, and may be in communication with a device controller 126 external to the non-volatile memory elements 123, a device driver, or the like. The dynamic read component 150 may operate on a non-volatile memory system 102 of a computing device 110, which may comprise a processor 111, volatile memory 112, and a communication interface 113. The processor 111 may comprise one or more central processing units, one or more general-purpose processors, one or more application-specific processors, one or more virtual processors (e.g., the computing device 110 may be a virtual machine operating within a host), one or more processor cores, or the like. The communication interface 113 may comprise one or more network interfaces configured to communicatively couple the computing device 110 and/or device controller 126 to a communication network 115, such as an Internet Protocol (IP) network, a Storage Area Network (SAN), wireless network, wired network, or the like.

The non-volatile memory device 120, in various embodiments, may be disposed in one or more different locations relative to the computing device 110. In one embodiment, the non-volatile memory device 120 comprises one or more non-volatile memory elements 123, such as semiconductor chips or packages or other integrated circuit devices disposed on one or more printed circuit boards, storage housings, and/or other mechanical and/or electrical support structures. For example, the non-volatile memory device 120 may comprise one or more direct inline memory module (DIMM) cards, one or more expansion cards and/or daughter cards, a solid-state-drive (SSD) or other hard drive device, and/or may have another memory and/or storage form factor. The non-volatile memory device 120 may be integrated with and/or mounted on a motherboard of the computing device 110, installed in a port and/or slot of the computing device 110, installed on a different computing device 110 and/or a dedicated storage appliance on the network 115, in communication with the computing device 110 over an external bus (e.g., an external hard drive), or the like.

The non-volatile memory device 120, in one embodiment, may be disposed on a memory bus of a processor 111 (e.g., on the same memory bus as the volatile memory 112, on a different memory bus from the volatile memory 112, in place of the volatile memory 112, or the like). In a further embodiment, the non-volatile memory device 120 may be disposed on a peripheral bus of the computing device 110, such as a peripheral component interconnect express (PCI Express or PCie) bus, a serial Advanced Technology Attachment (SATA) bus, a Parallel Advanced Technology Attachment (PATA) bus, a small computer system interface (SCSI) bus, a FireWire bus, a Fibre Channel connection, a Universal Serial Bus (USB), a PCie Advanced Switching (PCie-AS) bus, or the like. In another embodiment, the non-volatile memory device 120 may be disposed on a data network 115, such as an Ethernet network, an Infiniband network, SCSI RDMA over a network 115, a storage area network (SAN), a local area network (LAN), a wide area network (WAN) such as the Internet, another wired and/or wireless network 115, or the like.

The computing device 110 may further comprise a non-transitory, computer readable storage medium 114. The computer readable storage medium 114 may comprise executable instructions configured to cause the computing device 110 (e.g., processor 111) to perform steps of one or more of the methods disclosed herein. Alternatively, or in addition, the dynamic read component 150 may include one or more computer readable instructions stored on the non-transitory storage medium 114.

The non-volatile memory system 102, in the depicted embodiment, includes one or more dynamic read components 150. A dynamic read component 150, in one embodiment, is configured to monitor one or more read statistics during a read operation for data of a non-volatile memory element 123 or die, determine whether the one or more read statistics satisfy a threshold for the read operation, and dynamically modify the read operation based on determining that the one or more read statistics fail to satisfy the threshold.

In various embodiments, monitoring read statistics may allow a dynamic read component 150 to modify, adjust, or update a read operation to avoid or respond to errors, or error-causing phenomena. In certain embodiments, a device controller 126 external to the non-volatile memory elements 123 for a non-volatile memory device 120 may detect and respond to errors after a non-volatile memory element 123 has completed a read operation and transferred the data from the read operation to the device controller 126. By contrast, dynamically modifying a read operation using dynamic read components 150 at the level of the individual non-volatile memory elements 123 may reduce the amount of erroneous data sent over a shared bus 127, conserve time and power for an error-correcting code (ECC) decoder, facilitate parallel read operations for different non-volatile memory elements 123, and/or the like.

In one embodiment, a dynamic read component 150 may comprise logic hardware of a non-volatile memory element 123, other programmable logic, firmware for a for a non-volatile memory element 123, microcode for execution by a non-volatile memory element 123, or the like. In another embodiment, a dynamic read component 150 may comprise executable software code, stored on a computer readable storage medium for execution by logic hardware of a non-volatile memory element 123. In a further embodiment, a dynamic read component 150 may include a combination of both executable software code and logic hardware.

In one embodiment, the dynamic read component 150 is configured to receive storage requests from a device driver or other executable application via buses 125, 127, a device controller 126, or the like. The dynamic read component 150 may be further configured to transfer data to/from a device driver and/or storage clients 116 via the bus 125. Accordingly, the dynamic read component 150, in some embodiments, may comprise and/or be in communication with one or more direct memory access (DMA) modules, remote DMA modules, bus controllers, bridges, buffers, and so on to facilitate the transfer of storage requests and associated data. In another embodiment, the dynamic read component 150 may receive storage requests as an API call from a storage client 116, as an IO-CTL command, or the like. The dynamic read component 150 is described in further detail below with regard to FIG. 5 and FIG. 6.

According to various embodiments, a device controller 126 may manage one or more non-volatile memory devices 120 and/or non-volatile memory elements 123. The non-volatile memory device(s) 120 may comprise recording, memory, and/or storage devices, such as solid-state storage device(s) and/or semiconductor storage device(s) that are arranged and/or partitioned into a plurality of addressable media storage locations. As used herein, a media storage location refers to any physical unit of memory (e.g., any quantity of physical storage media on a non-volatile memory device 120). Memory units may include, but are not limited to: pages, memory divisions, blocks, sectors, collections or sets of physical storage locations (e.g., logical pages, logical blocks), or the like.

A device driver and/or the device controller 126, in certain embodiments, may present a logical address space 134 to the storage clients 116. As used herein, a logical address space 134 refers to a logical representation of memory resources. The logical address space 134 may comprise a plurality (e.g., range) of logical addresses. As used herein, a logical address refers to any identifier for referencing a memory resource (e.g., data), including, but not limited to: a logical block address (LBA), cylinder/head/sector (CHS) address, a file name, an object identifier, an inode, a Universally Unique Identifier (UUID), a Globally Unique Identifier (GUID), a hash code, a signature, an index entry, a range, an extent, or the like.

A device driver for the non-volatile memory device 120 may maintain metadata 135, such as a logical to physical address mapping structure, to map logical addresses of the logical address space 134 to media storage locations on the non-volatile memory device(s) 120. A device driver may be configured to provide storage services to one or more storage clients 116. The storage clients 116 may include local storage clients 116 operating on the computing device 110 and/or remote, storage clients 116 accessible via the network 115 and/or network interface 113. The storage clients 116 may include, but are not limited to: operating systems, file systems, database applications, server applications, kernel-level processes, user-level processes, applications, and the like.

A device driver may be communicatively coupled to one or more non-volatile memory devices 120. The one or more non-volatile memory devices 120 may include different types of non-volatile memory devices including, but not limited to: solid-state storage devices, semiconductor storage devices, SAN storage resources, or the like. The one or more non-volatile memory devices 120 may comprise one or more respective device controllers 126 and non-volatile memory media 122. A device driver may provide access to the one or more non-volatile memory devices 120 via a traditional block I/O interface 131. Additionally, a device driver may provide access to enhanced functionality through the SCM interface 132. The metadata 135 may be used to manage and/or track data operations performed through any of the Block I/O interface 131, SCM interface 132, cache interface 133, or other, related interfaces.

The cache interface 133 may expose cache-specific features accessible via a device driver for the non-volatile memory device 120. Also, in some embodiments, the SCM interface 132 presented to the storage clients 116 provides access to data transformations implemented by the one or more non-volatile memory devices 120 and/or the one or more device controllers 126.

A device driver may present a logical address space 134 to the storage clients 116 through one or more interfaces. As discussed above, the logical address space 134 may comprise a plurality of logical addresses, each corresponding to respective media locations the on one or more non-volatile memory devices 120. A device driver may maintain metadata 135 comprising any-to-any mappings between logical addresses and media locations, or the like.

A device driver may further comprise and/or be in communication with a non-volatile memory device interface 139 configured to transfer data, commands, and/or queries to the one or more non-volatile memory devices 120 over a bus 125, which may include, but is not limited to: a memory bus of a processor 111, a peripheral component interconnect express (PCIExpress or PCie) bus, a serial Advanced Technology Attachment (ATA) bus, a parallel ATA bus, a small computer system interface (SCSI), FireWire, Fibre Channel, a Universal Serial Bus (USB), a PCie Advanced Switching (PCie-AS) bus, a network 115, Infiniband, SCSI RDMA, or the like. The non-volatile memory device interface 139 may communicate with the one or more non-volatile memory devices 120 using input-output control (10-CTL) command(s), IO-CTL command extension(s), remote direct memory access, or the like.

The communication interface 113 may comprise one or more network interfaces configured to communicatively couple the computing device 110 and/or the device controller 126 to a network 115 and/or to one or more remote, network-accessible storage clients 116. The storage clients 116 may include local storage clients 116 operating on the computing device 110 and/or remote, storage clients 116 accessible via the network 115 and/or the network interface 113. The device controller 126 is part of and/or in communication with one or more non-volatile memory devices 120. Although Figure I depicts a single non-volatile memory device 120, the disclosure is not limited in this regard and could be adapted to incorporate any number of non-volatile memory devices 120.

The non-volatile memory device 120 may comprise one or more elements 123 of non-volatile memory media 122, which may include but is not limited to: ReRAM, Memristor memory, programmable metallization cell memory, phase-change memory (PCM, PCME, PRAM, PCRAM, ovonic unified memory, chalcogenide RAM, or C-RAM), NAND flash memory (e.g., 2D NAND flash memory, 3D NAND flash memory), NOR flash memory, nano random access memory (nano RAM or NRAM), nanocrystal wire-based memory, silicon-oxide based sub-IO nanometer process memory, graphene memory, Silicon-Oxide-Nitride-Oxide-Silicon (SONOS), programmable metallization cell (PMC), conductive-bridging RAM (CBRAM), magneto-resistive RAM (MRAM), magnetic storage media (e.g., hard disk, tape), optical storage media, or the like. The one or more elements 123 of non-volatile memory media 122, in certain embodiments, comprise storage class memory (SCM).

While legacy technologies such as NAND flash may be block and/or page addressable, storage class memory, in one embodiment, is byte addressable. In further embodiments, storage class memory may be faster and/or have a longer life (e.g., endurance) than NAND flash; may have a lower cost, use less power, and/or have a higher storage density than DRAM; or offer one or more other benefits or improvements when compared to other technologies. For example, storage class memory may comprise one or more non-volatile memory elements 123 of ReRAM, Memristor memory, programmable metallization cell memory, phase-change memory, nano RAM, nanocrystal wire-based memory, silicon-oxide based sub-IO nanometer process memory, graphene memory, SONOS memory, PMC memory, CBRAM, MRAM, and/or variations thereof.

While the non-volatile memory media 122 is referred to herein as “memory media,” in various embodiments, the non-volatile memory media 122 may more generally comprise one or more non-volatile recording media capable of recording data, which may be referred to as a non-volatile memory medium, a non-volatile storage medium, or the like. Further, the non-volatile memory device 120, in various embodiments, may comprise anon-volatile recording device, a non-volatile memory device, a non-volatile storage device, or the like. Similarly, a non-volatile memory element 123, in various embodiments, may comprise a non-volatile recording element, a non-volatile memory element, a non-volatile storage element, or the like.

The non-volatile memory media 122 may comprise one or more non-volatile memory elements 123, which may include, but are not limited to: chips, packages, planes, die, or the like. A device controller 126, external to the one or more non-volatile memory elements 123, may be configured to manage data operations on the non-volatile memory media 122, and may comprise one or more processors, programmable processors (e.g., FPGAs), ASICs, micro-controllers, or the like. In some embodiments, the device controller 126 is configured to store data on and/or read data from the non-volatile memory media 122, to transfer data to/from the non-volatile memory device 120, and so on.

The device controller 126 may be communicatively coupled to the non-volatile memory media 122 by way of a bus 127. The bus 127 may comprise an I/O bus for communicating data to/from the non-volatile memory elements 123. The bus 127 may further comprise a control bus for communicating addressing and other command and control information to the non-volatile memory elements 123. In some embodiments, the bus 127 may communicatively couple the non-volatile memory elements 123 to the device controller 126 in parallel. This parallel access may allow the non-volatile memory elements 123 to be managed as a group, forming a logical memory element 129. The logical memory element may be partitioned into respective logical memory units (e.g., logical pages) and/or logical memory divisions (e.g., logical blocks). The logical memory units may be formed by logically combining physical memory units of each of the non-volatile memory elements.

The device controller 126 may comprise and/or be in communication with a device driver executing on the computing device 110. A device driver may provide storage services to the storage clients 116 via one or more interfaces 131, 132, and/or 133. In some embodiments, a device driver provides a block-device I/O interface 131 through which storage clients 116 perform block-level I/O operations. Alternatively, or in addition, a device driver may provide a storage class memory (SCM) interface 132, which may provide other storage services to the storage clients 116. In some embodiments, the SCM interface 132 may comprise extensions to the block device interface 131 (e.g., storage clients 116 may access the SCM interface 132 through extensions or additions to the block device interface 131). Alternatively, or in addition, the SCM interface 132 may be provided as a separate API, service, and/or library. A device driver may be further configured to provide a cache interface 133 for caching data using the non-volatile memory system 102.

A device driver may further comprise a non-volatile memory device interface 139 that is configured to transfer data, commands, and/or queries to the device controller 126 over a bus 125, as described above.

FIG. 2 illustrates an embodiment of a non-volatile storage device 210 that may include one or more memory die or chips 212. The nonvolatile storage device 210 may be substantially similar to the nonvolatile memory device 120 described with reference to FIG. 1. Memory die 212, in some embodiments, includes an array (two-dimensional or three dimensional) of memory cells 200, on-die controller 220, and read/write circuits 230A/230B. In one embodiment, access to the memory array 200 by the various peripheral circuits is implemented in a symmetric fashion, on opposite sides of the array, so that the densities of access lines and circuitry on each side are reduced by half. The read/write circuits 230A/230B, in a further embodiment, include multiple sense blocks 250 which allow a page of memory cells to be read or programmed in parallel.

The memory array 200, in various embodiments, is addressable by word lines via row decoders 240A/240B and by bit lines via column decoders 242A/242B. In some embodiments, a device controller 126 external to the memory die 212 is included in the same memory device 210 (e.g., a removable storage card or package) as the one or more memory die 212. Commands and data are transferred between the host and the device controller 126 via lines 232 and between the device controller 126 and the one or more memory die 212 via lines 234. One implementation can include multiple chips 212.

On-die controller 220, in one embodiment, cooperates with the read/write circuits 230A/230B to perform memory operations on the memory array 200. The on-die controller 220, in certain embodiments, includes a dynamic read component 150, a state machine 222, an on-chip address decoder 224, and a power control circuit 226. The dynamic read component 150, in one embodiment, is configured to monitor one or more read statistics during a read operation for data of the memory array 200, determine whether the one or more read statistics satisfy a threshold for the read operation, and dynamically modify the read operation based on determining that the one or more read statistics fail to satisfy the threshold.

The state machine 222, in one embodiment, provides chip-level control of memory operations. The on-chip address decoder 224 provides an address interface to convert between the address that is used by the host or a device controller 126 to the hardware address used by the decoders 240A, 240B, 242A, 242B. The power control circuit 226 controls the power and voltages supplied to the word lines and bit lines during memory operations. In one embodiment, power control circuit 226 includes one or more charge pumps that can create voltages larger than the supply voltage.

In certain embodiments, the state machine 222 includes an embodiment of the dynamic read component 150. The dynamic read component 150, in certain embodiments, may include software, firmware, or hardware in an on-die controller 220 and/or a state machine 222.

In one embodiment, one or any combination of on-die controller 220, dynamic read component 150, power control circuit 226, decoder circuit 224, state machine circuit 222, decoder circuit 242A, decoder circuit 242B, decoder circuit 240A, decoder circuit 240B, read/write circuits 230A, read/write circuits 230B, and/or device controller 126 can be referred to as one or more managing circuits.

FIGS. 3A, 3B, 3C, and 3D are graphs 300, 320, 340, 360 depicting distributions of threshold voltages for storage cells of a non-volatile memory element 123. In the depicted embodiment, the graphs 300, 320, 340, 360 illustrate a plurality of read thresholds 302, 322, 342, 362 that divide a range of possible threshold voltages for the cells into states LO, LI, L2, L3.

As used herein, a “cell” refers to the smallest physical unit of storage or memory in a non-volatile memory element 123. In some embodiments, each cell has a physical and/or electrical property which may be altered to encode or otherwise store data. For example, in flash memory, a cell may include a floating gate transistor, and the physical property used to encode data may be the charge stored on the floating gate, a stored read voltage level caused by the charge stored on the floating gate, the threshold voltage Vt that is sufficient to make the transistor conduct when applied to the control gate, or the like. As another example, in phase change memory, a cell may be a region of chalcogenide glass, and the physical property used to encode data may be the degree of crystallization of the region, the electrical resistance of the cell, or the like. Various types of storage cells for various types of non-volatile memory will be clear in view of this disclosure.

In the depicted embodiment, the storage cells are flash memory cells (e.g., floating gate transistors), and the data-encoding physical property is the threshold voltage Vt. The depiction of distributions, read thresholds 302, 322, 342, 362 and states LO, LI, L2, L3 in relation to a threshold voltage Vt is for illustrative and non-limiting purposes; the disclosure may be similarly applicable to read thresholds and states for another data-encoding physical property, for another type of non-volatile memory. The threshold voltage Vt is shown on the horizontal axis of each of the graphs 300, 320, 340, 360, and the vertical axis illustrates a number of cells, so that the graphs 300, 320, 340, 360 show the numbers of cells at various threshold voltages Vt.

In the depicted embodiment, read thresholds 302, 322, 342, 362, divide a range of possible values for the threshold voltage Vt into states LO, L1, L2, L3. In the depicted embodiment, multi-level cell (MLC) flash memory cells use four states LO, L1, L2, L3 to store two bits per cell. However, in another embodiment, a range of possible values for a threshold voltage Vt (or other data-encoding physical property) may be divided into more or fewer states, to store more or fewer bits per cell. In one embodiment, an encoding maps states onto data values. For example, in the depicted embodiment, a Gray code encoding maps the four states LO, L1, L2, and L3 to the data values “11,” “01,” “00,” and “10,” respectively. In another embodiment, another encoding may map states to data values in another way.

In FIG. 3A, the graph 300 depicts an initial distribution of threshold voltages Vt when data is written to cells of a non-volatile memory element 123. In the depicted embodiment, the distribution forms a bell-shaped peak in each state. In some embodiments, a cell may be programmed to a state by issuing voltage pulses that move the threshold voltage Vt for the cell to or near a target voltage for that state. Thus, a bell-shaped peak may be centered on the target programming voltage, or the like. The width of the peaks may be affected by variations in the cells and the programming process, or by error-causing phenomena such as read disturbs, program disturbs, stress-induced leakage current, or the like. Although symmetric, bell-shaped peaks are shown, skewed distributions and other distributions are possible. Over time, the distributions may widen or skew as the threshold voltages Vt of cells move from their originally programmed values.

Additionally, graph 300 depicts a substantially uniform distribution among states LO-L3 (e.g., there are approximately the same number of cells in each state LO-L3). In certain embodiments, a known balance among states (e.g., a uniform or known distribution among states) may result from encoding or transforming data with a known balance between ones and zeros. For example, if data is transformed according to a scrambling or whitening transformation so that an approximately equal number of binary zeros and ones are stored, then writing data to the cells may also result in an approximately equal number of cells in each state. In another embodiment, data may be written with another known balance between ones and zeros, or between states.

In one embodiment, a read operation may include sensing whether the data-encoding physical property of a cell (e.g., the threshold voltage Vt) is above or below a read threshold 302. For example, a read voltage may be applied to the control gate of a floating gate transistor storage cell at the level of the first read threshold 302 a. If the cell turns on (e.g., conducts between source and drain terminals), then the threshold voltage Vt for the storage cell is lower than first read threshold 302 a, and the cell is in the LO state. If the cell does not turn on when the first read voltage is applied, but turns on when a read voltage is applied at the level of the second read threshold 302 b, then the cell is in the LI state, and so on. In another embodiment, a ramping voltage (e.g., a voltage signal that increases linearly from 0 V to 12 V, or the like) may be applied to the control gate, and sense amplifiers may determine when (or at what voltage) the cell turns on.

In FIG. 3A, the graph 300 depicts narrow and well-separated peaks, centered in states LO, LI, L2, and L3. As depicted, an initial distribution of threshold voltages Vt when data is written may include narrow peaks, due to cells being close to a target programming voltage. Thus, a read operation using read thresholds 302 a, 302 b, and 302 c should retrieve the data as written, with few errors. However, the peaks may widen over time, as the threshold voltage Vt for individual cells may drift in either direction due to phenomena such as program disturbs, read disturbs, temperature effects, or the like. Additionally, the peaks may also shift towards lower voltages over time, as the threshold voltage Vt for individual cells may drift lower due to charge leakage.

In FIG. 3B, the graph 320 depicts a distribution of threshold voltages Vt for the same cells as FIG. 3A, at a later time. The peaks in graph 320 have shifted lower due to charge leakage. However, the read thresholds 322 that define the boundaries between states LO-L3 are at the same voltages as the read thresholds in FIG. 3A. Thus, a read operation will return data with errors, as some of the cells that were programmed to the L3 state will now be sensed in the L2 state, some of the cells that were programmed to the L2 state will now be sensed in the LI state, and so on.

In a certain embodiment, a dynamic read component 150 may monitor one or more read statistics, such as a count or proportion of ones, a count or proportion of zeros, a ratio between ones and zeros, a count or proportion of cells for any of the states LO-L3, a ratio of cells in different states, or the like, during a read operation. In further embodiments, certain read statistics may correspond to shifting or widening peaks. For example, in the depicted embodiment, the number of cells in state LO is greater than when the data was written (as depicted in graph 300 of FIG. 3A), and the number of cells in state L3 is less than when the data was written, due to threshold voltages Vt for the cells drifting in a negative direction, past the established read thresholds 322. Thus, monitoring the number of cells in state LO or L3 may suggest that the peaks have shifted as shown in graph 320.

In a certain embodiment, the dynamic read component 150 may determine whether the one or more read statistics satisfy a threshold. A threshold for a read statistic may be a value to which the read statistic is compared, to determine whether the read statistic is within an expected, allowed, or acceptable range (e.g., satisfies the threshold), or is outside of an expected, allowed, or acceptable range (e.g., fails to satisfy the threshold). In certain embodiments, a threshold for a read statistic may be selected or set by a manufacturer of a non-volatile storage element 123, a user or administrator of a non-volatile memory device 120, or the like, based on an expected or desired range for the read statistic. For example, in one embodiment, if data is read from groups of 512 cells at a time, and if data is stored subject to a scrambling or whitening transformation, then 128 cells (e.g., one quarter of the cells for the read operation) may be expected to be in state LO. A small variation in the number of cells in the LO state may be attributable to randomness in the scrambling or whitening transformation. However, a larger imbalance in the number of cells in the LO state may suggest that the peaks have shifted as shown in FIG. 3B. Thus, if the read statistic(s) monitored by the dynamic read component 150 during a read operation include the number of cells in the LO state, and a threshold for that read statistic is established at slightly more than a quarter of the number of cells read during a read operation, than the statistic failing to satisfy the threshold may indicate that the peaks have shifted, and that errors are likely. Accordingly, in certain embodiments, a dynamic read component 150 may dynamically modify a read operation.

In FIG. 3C, the graph 340 depicts the same distribution of threshold voltages Vt as the graph 320 of FIG. 3B, but with read thresholds 342 at different voltages than the read thresholds 322 of FIG. 3B. In one embodiment, a dynamic read component 150 may dynamically modify a read operation by changing one or more of the read thresholds 342. For example, if the dynamic read component 150 detects (based on read threshold 322 a in FIG. 3B) that the number of cells in state LO exceeds a threshold, it may modify the read operation to use new read thresholds (such as 342 a, 342 b 342 c in FIG. 3C) shifted to lower voltages to compensate for threshold voltages Vt for the cells drifting in a negative direction.

In FIG. 3D, the graph 360 depicts a distribution of threshold voltages Vt for the same cells as FIG. 3A, at a later time. The read thresholds 362 that define the boundaries between states LO-L3 are depicted at the same voltages as the read thresholds in FIG. 3A. However, the peaks in graph 360 have both drifted in the negative voltage direction (as in FIG. 3B), and widened over time due to the threshold voltage Vt drifting for individual cells. As in FIG. 3B, a cell that has drifted past one of the read thresholds 362 may have drifted into an adjacent state. For example, a cell originally in the LO state after data was written may now be sensed in the LI stat due to the peaks widening. (The distribution is depicted as a set of overlapping peaks to emphasize the possibility that a cell programmed to one state may drift into an adjacent state; an actual distribution may be the sum of the individual peaks).

In certain embodiments, a dynamic read component 150 may dynamically modify a read operation by obtaining soft bits indicating a reliability of the data. For example, FIG. 3D depicts the read thresholds 362 that define the boundaries between states LO-L3, and additional read voltages 364 near the read thresholds. Sensing whether a threshold voltage Vt for a cell is above or below one of the read thresholds 362 may determine a state for the cell, and sensing whether a threshold voltage Vt for a cell is above or below one or more of the additional read voltages 364 may determine a likelihood that the cell was originally programmed to (or left erased in) it's current state.

For example, sensing that a threshold voltage Vt for a cell is below the read threshold 362 a that divides the LO and LI states may indicate that the cell is in the LO state, and stores the data value “11.” However, the cell may have drifted from the LI state, storing the data value “01.” The second bit (storing a 1) may therefore be reliable, since it is unlikely that the cell drifted from the L2 or L3 states. In a further embodiment, sensing whether the threshold voltage Vt for a cell is above or below one or more additional read voltages 364 near the read threshold 362 a may indicate a reliability for the first bit (which stores a 1 in the LO state, but which stores a 0 in the LI state, from which the cell may have drifted). For example, if the threshold voltage Vt is well below the read threshold 362 a, then the cell was likely originally in the LO state when data was written. However, if the threshold voltage Vt is below the read threshold 362 a, but above a nearby additional read voltage 364, then it still may have been originally in the LO state when data was written, but also is more likely to have been originally programmed to the LI state. A “soft bit” may indicate a reliability of a data value based on the additional read voltages 364 in a variety of ways, and may be a likelihood that a bit is correct, a likelihood that a bit is incorrect, a log-likelihood ratio, or the like.

FIG. 4 is a schematic block diagram 400 illustrating one embodiment of an internal read size 402 in relation to a data transfer size 404. In certain embodiments, a read command sent to a non-volatile memory element 123 may be for a chunk, block, page, or other unit of data, at a data transfer size 404 expected or requested by a device controller 126 external to the non-volatile memory element 123 or die. In various embodiments, a data transfer size 404 may refer to an amount of data read from a non-volatile memory element 123 and transferred to a device controller 126 in response to a single read command. Within a non-volatile memory element 123, however, the read command may be internally serviced by performing a plurality of read operations at a smaller internal read size 403. An internal read size 402, or a data size for a read operation, may refer to an amount of data that is read internally as a single unit. For example, in flash memory, word lines may be coupled to control gates across rows of cells, so that data is read from a set of cells coupled to the same word line in a single read operation.

In certain embodiments, as depicted in FIG. 4, the data size for a read operation (e.g., internal read size 402) is smaller than a data transfer size 404 between a non-volatile memory element 123 and a device controller 126. For example, a 4 KiB page to be transferred to the device controller 126 may be assembled from the data of four smaller 1 KiB internal reads. Various other ratios between an internal read size 402 and a data transfer size 404 may exist for other non-volatile memory elements 123 and device controllers 126. In certain embodiments, a dynamic read component 150 may be disposed on a die for a non-volatile memory element, and may monitor read statistics and dynamically modify read operations for internal read operations, at the smaller internal read size 402. In further embodiments, monitoring read statistics and dynamically modifying read operations on-die (e.g., during read operations at the internal read size 402) may allow a dynamic read component 150 to more accurately detect and indicate where errors are located, stop additional internal read operations early if an error rate is high, or the like.

FIG. 5 depicts one embodiment of a dynamic read component 150. The dynamic read component 150 may be substantially similar to the dynamic read component 150 described above with regard to FIG. 1 and FIG. 2. In general, as described above, the dynamic read component 150 is configured to dynamically modify, adjust, or update a read operation based on one or more read statistics. In the depicted embodiment, the dynamic read component 150 includes a statistics circuit 502, a threshold circuit 504, and an adjustment circuit 506.

In a certain embodiment, an on-die controller for a non-volatile memory die, such as the on-die controller 220 of FIG. 2, may include the statistics circuit 502, the threshold circuit 504, and the adjustment circuit 506. In certain embodiments, a die may be a semiconductor device of non-volatile memory. In various embodiments, a die may refer to an integrated circuit that includes both a core array of non-volatile memory cells and peripheral components for communicating with the core. In one embodiment, such an integrated circuit may be a three-dimensional integrated circuit that includes multiple die planes and/or layers, but may still be referred to as a die. As described with regard to FIGS. 1-2, a non-volatile memory device 120 may include one or more non-volatile memory elements 123 or dies.

In various embodiments, an on-die controller 220 may refer to a component on a die, control/operation logic on a die, a set of components on a die, or the like, that controls data operations for a memory array 200 on the die. In certain embodiments, an on-die controller 220 comprising a statistics circuit 502, a threshold circuit 504, and an adjustment circuit 506 may conserve resources of a device controller 126 external to a die, such as decoder time and power, by dynamically modifying, adjusting, or updating a read operation at the die level (and possibly during the read operation). By contrast, a device controller 126 external to a die may modify a second read operation after receiving data of a first read operation, but waiting for the first read operation to complete and for the data to be transferred consumes more time and transfers more data over a bus 127 than dynamically modifying a read operation at the die level.

The statistics circuit 502, in one embodiment, is configured to monitor one or more read statistics during a read operation for data of a non-volatile memory die. In various embodiments, a read operation may refer to any operation or process that reads, senses, or retrieves data from a non-volatile memory die. In certain embodiments, the dynamic read component 150 or on-die controller 220 may initiate a read operation in response to a read command from a device controller 126. In another embodiment, the dynamic read component 150 or on-die controller 220 may initiate a read operation as part of a grooming or garbage collection operation, or the like. In one embodiment, data may be read from a group of storage cells (such as cells coupled to a word line) together, and data for a read operation may have a fixed size, such as the internal read size 402 of FIG. 4. In another embodiment, (e.g., for a type of non-volatile medium other than flash memory), a read operation for a non-volatile die may be for a variable amount of data. In one embodiment, a “read operation” may refer to a single internal read. In another embodiment, a read operation may refer to a series of internal reads that retrieve a larger unit of data for transferring data to the device controller 126.

A “read statistic” as used herein, may refer to any information about the read operation that may be collected, monitored, tracked, or calculated by the statistics circuit 502. Various types of read statistics for read operations may pertain to the read operation at various levels of abstraction, from the physical data-encoding property of a storage cell (e.g., a threshold voltage Vt for flash memory), to states (e.g., subranges of the data-encoding property defined by read thresholds), to bits that correspond to the states, or the like. For example, in one embodiment, ramp word line sensing may include determining threshold voltages Vt for a set of storage cells before converting the voltages to states or bits, and a voltage statistic may include any statistic relating to the voltages, such as an average voltage, a standard deviation for the voltages, a count of voltages less than a first read threshold, a ratio of voltages less than a first read threshold to voltages greater than a first read threshold or the like.

As a further example, a read statistic may be a balance between or among states, a balance between zeros and ones, or the like. As used herein, a “balance” may refer to any measurement or indicator that measures or relates to a ratio between zeros and ones, a ratio of cells in different states, or the like. For example, a “balance” between zeros and ones may refer to a proportion of zeros in the data of a read operation, a proportion of ones in the data of a read operation, a ratio of ones to zeros, a ratio of zeros to ones, a count of ones, a count of zeros, a difference between a count of ones and a count of zeroes, an average data value (between one and zero) or the like. Similarly, a “balance” between or among states may refer to a count or proportion of cells in any one of the states, a ratio of cells in one state to cells in another state, or the like. In certain embodiments, the statistics circuit 502 may track or monitor one or more read statistics, of one or more different types, such as a balance of zeros and ones and a balance of states. Various further types of read statistics will be clear in view of this disclosure.

In certain embodiment, data of a non-volatile memory element 123 or die may be written or stored subject to a data transformation that balances bit values (e.g., ones and zeros) for the data. A transformation may refer to any function, mapping, encoding, or the like that is applied to store the data. For example, a data transformation may include applying an error correcting code, encrypting the data, compressing the data, scrambling or whitening the data, or the like. In certain embodiments, data transformations may balance bit values. A transformation that balances bit values may refer to any transformation that produces an approximately equal number of zeros and ones in the transformed data. For example, a block of zeros may be transformed to a sequence of ones and zeros. In one embodiment, transforming one block or chunk of data with a transformation that balances bit values may produce a block or chunk of transformed data in which the number of ones and zeros are not exactly equal, however, the transformation may produce an equal number of ones and zeros on average. Similarly, a variance and/or standard deviation for the number of ones or zeros produced by a data transformation may be known. In another embodiment, a data transformation may encode bits to states in a way that balances the states (e.g., so that the LO, LI, L2, and L3 states occur equally often).

In a certain embodiment, a data transformation may balance bit values, or may produce a predetermined or known balance of bit values. For example, one data transformation may produce a proportion of 50% zeros in the transformed data. Another transformation may be known to produce a proportion of 40% zeros in the transformed data. Similarly, a transformation may balance states (e.g., 25% of cells in each of four states) or may produce a known balance of states. In various embodiments, where data is written, stored, or programmed with a known balance between ones and zeros, a known balance among states or the like, or another known characteristic of a data transformation, a read statistic monitored by the statistics circuit 502 may include the balance or characteristic that is known for the data transformation. In a further embodiment, comparing the actual balance or characteristic obtained during a read operation to a known or expected balance or characteristic may indicate or suggest an error rate. Thus, using a statistics circuit 502 to monitor one or more read statistics may allow a dynamic read component 150 to modify, update, or adjust a read operation based on the one or more monitored read statistics.

In one embodiment, a read statistic monitored or tracked by a statistics circuit 502 comprises a balance between zeros and ones for at least a portion of the data of the read operation. In a certain embodiment, the statistics circuit 502 may track an ongoing balance between bit values for the data during the read operation. In various embodiments, the statistics circuit 502 may track one or more statistics on an ongoing basis, or for a portion of data of a read operation, in various ways. For example, a statistics circuit 502 may include a register, accumulator, or the like, used to store or count the number of ones (or the number of zeros) in the data as the data is read. In certain embodiments, a read operation may include a number of sub-operations. For example, referring to FIG. 3A, a read-operation for MLC flash memory may first include reading the second bit depicted in FIG. 3A (1 for the LO and LI states, 0 for the L2 and L3 states), by detecting whether threshold voltages Vt for a group of cells are above or below the central read threshold 302 b. The read operation may then include sensing the first bit using read thresholds 302 a and 302 c. Thus, a balance of zeros and ones may be determined for a portion of the data (e.g., the second bit) on an ongoing basis, before both bits are obtained. Similarly, in another embodiment, a read operation may include sensing whether threshold voltages Vt for a group of cells are above or below the read thresholds 302 a, 302 b, 302 c in order, and the number or proportion of cells in the LO state may be obtained before the number or proportion of cells in the other states. Thus, tracking an ongoing balance between or among states may include obtaining a count or proportion of cells in one of the states before the number or proportion of cells in another state is obtained.

In various embodiments, the statistics circuit 502 may obtain or calculate numeric information to monitor or track a read statistic. For example, in one embodiment, monitoring a read statistic may include obtaining a count of ones, a count of zeros or the like. In another embodiment, monitoring a read statistic may include calculating a difference between counts of ones and zeroes, a ratio between counts of ones and zeros or the like. Various ways to monitor a read statistic by obtaining or calculating numeric information will be clear in view of this disclosure.

The threshold circuit 504, in one embodiment, is configured to determine whether the one or more read statistics monitored by the statistics circuit 502 satisfy a threshold for the read operation. For example, in one embodiment, the threshold circuit 504 may compare the one or more read statistics to one or more expected statistics for the data.

In general, in various embodiments, the on-die controller 220 or dynamic read component 150 may proceed normally with a read operation if the read statistic(s) are normal, within an expected or acceptable range, or the like, and may modify, adjust or update a read operation if one or more of the read statistics are outside of acceptable ranges. A “threshold” for a read statistic, in various embodiments, may be a value or set of values to which the read statistic is compared, to determine whether the read statistic is within an expected, allowed, or acceptable range. For example, in one embodiment a threshold may be a maximum allowed value for a read statistic. In another embodiment, a threshold may be a minimum acceptable value for a read statistic. In a further embodiment, a threshold may be a pair of maximum and minimum values establishing an acceptable range for a read statistic. Various further types of thresholds for read statistics will be clear in view of this disclosure. A read statistic is said to satisfy the threshold if the read statistic is acceptable in comparison to the threshold (e.g., is below a maximum, above a minimum, within a range, or the like), and fails to satisfy the threshold otherwise.

In certain embodiments, a threshold for a plurality of read statistics may include a set of thresholds for individual read statistics, so that the plurality of read statistics fails to satisfy the threshold if any of the individual read statistics fails to satisfy a corresponding individual threshold. In various embodiments, the threshold circuit 504 may determine whether one or more read statistics satisfies a threshold by comparing the one or more read statistics to a threshold. In one embodiment, a threshold circuit 504 may include logic hardware for comparing a statistic to a threshold, as well as memory, a register, or the like for storing a threshold, a statistic, and/or a result, and the like.

In a certain embodiment, a threshold circuit 504 may compare one or more read statistics to one or more expected read statistics. In various embodiments, an expected read statistic may refer to a known or inferred statistic relating to the data when it was written. For example, in one embodiment, an expected read statistic may be inferred from a known property or characteristic of a data transformation applied to the data before storing the data. As a further example, an expected statistic for a data transformation that balances bit values may be 50% zeroes, 512 zeroes for a 1024 bit unit of data, 500-524 zeros for a 1024 bit unit of data (where a standard deviation for the number of zeros produced by the data transformation is known), or the like. In another example, an expected statistic may be a measured statistic from when the data was written. For example, in one embodiment, an actual balance of ones and zeroes may be measured when the data is written, and stored with other metadata for the data.

In one embodiment, as described above, a threshold used by the threshold circuit 504 may be based on a balance between ones and zeros for data written with a known balance between ones and zeros. In another embodiment, a threshold used by the threshold circuit 504 may be based on a balance among states for storage cells programmed with a known balance of states. For example, where data is programmed subject to a transformation that results in the states LO-L3 occurring equally often, a threshold may be based on an expected 25% of cells in the LO state. In a further embodiment, a threshold used by the threshold circuit 504 may be based on a voltage statistic for the read operation. For example, a threshold may be based on a count, average, grouping or the like of voltages, prior to converting the voltages to states or bits. In one embodiment, a threshold for a plurality of read statistics may be based on one or more of a balance between ones and zeros, a balance among states, and/or a voltage statistic. In various embodiments, using a threshold circuit 504 to compare actual read statistics to expected read statistics may allow the dynamic read component 150 to determine when to update or modify a read operation.

The adjustment circuit 506, in one embodiment, is configured to dynamically modify the read operation based on the threshold circuit 504 determining that the one or more read statistics monitored by the statistics circuit 502 fail to satisfy a threshold. example, the adjustment circuit 506 may adjust a read operation based on a tracked ongoing balance between bit values, or may update a read operation based on a variance between the one or more monitored read statistics and one or more expected read statistics for the data. A variance, in certain embodiments, may refer to any measure of divergence or discrepancy between monitored and expected read statistics.

In various embodiments, modifying, updating, or adjusting a read operation may refer to changing the read operation in any way. In certain embodiments, the adjustment circuit 506 may adjust a read operation by stopping or aborting the read operation, adjusting one or more read parameters for the read operation, or the like. Stopping the read operation and adjusting read operation parameters are described in further detail below with reference to the abort circuit 602 and the change circuit 604 of FIG. 6.

In various embodiments, an adjustment, modification, or update to a read operation may be referred to as “dynamic” if it occurs during a set of one or more read operations performed on a non-volatile memory element 123 or die, without the modification being specifically requested by a device controller 126 or driver external to the non-volatile memory element 123 or die. For example, a dynamic modification may be made by the adjustment circuit 506 during or within a read operation. In addition, or alternatively, a read operation may include multiple sub-operations such as sense operations at different read thresholds, internal reads of small units of data, or the like, and a dynamic modification may occur after one or more of the sub-operations but may affect other sub-operations. By contrast, a non-dynamic modification to read parameters may be made by a device controller 126 or driver external to a non-volatile memory element 123 or die, after receiving data of a first read operation. In various embodiments, using an on-die adjustment circuit 506 to dynamically adjust a read operation may allow prompt adjustments to be made, avoiding a round-trip of data out to a device controller 126 and modifications back from a device controller 126.

In various embodiments, using an adjustment circuit 506 to dynamically adjust a read operation may improve one or more read statistics for the data. For example, referring to FIG. 3B and FIG. 3C, dynamically adjusting a read operation to change read thresholds from the read thresholds 322 of FIG. 3B to the read thresholds 342 of FIG. 3C may improve a read statistic such as a balance between ones and zeros, a balance among states, or the like. In a further embodiment, dynamically adjusting a read operation may improve an error rate for the data. In various embodiments, using an adjustment circuit 506 to dynamically modify a read operation based on read statistics may improve error rates, conserve decoder time and power, reduce usage of a shared bus, or the like. In a further embodiment, multiple adjustment circuits 506 on different non-volatile memory elements 123 or die may operate in parallel, providing speed advantages over a device controller 126 external to a die non-dynamically modifying read parameters for one die at a time.

FIG. 6 depicts another embodiment of a dynamic read component 150. The dynamic read component 150, in certain embodiments, may be substantially similar to the dynamic read component 150 described above with regard to FIG. 1, FIG. 2, and/or FIG. 5. In the depicted embodiment, the dynamic read component 150 includes a statistics circuit 502, a threshold circuit 504, and an adjustment circuit 506, which may be configured substantially as described above with regard to FIG. 5. The adjustment circuit 506, in the depicted embodiment, includes an abort circuit 602 and a change circuit 604. The dynamic read component 150, in the depicted embodiment, includes a status circuit 606.

In one embodiment, dynamically modifying a read operation may include stopping the read operation without transferring the data of the read operation from the non-volatile memory die to a device controller 126. In a certain embodiment, the adjustment circuit 506 uses the abort circuit 602 to stop a read operation without transferring data to a device controller 126. In certain embodiments, dynamically stopping a read operation may avoid wasting time on completing a read operation for uncorrectable data. For example, in one embodiment, data may be written subject to a transformation that results in a balanced number of states (e.g., approximately 25% of the cells in a group of cells will be in any state). If sensing at a first read threshold reveals that a very large or very small number of cells are in the first state, then the data may have a larger number of errors than a decoder can correct, and using an abort circuit 602 to stop the read operation may save time that would be spent on sensing at further read thresholds, as well as time and power to transmit and attempt to decode the data. Similarly, in another embodiment, a read operation may include a hard read that determines bit values, and a soft read (e.g., using the additional read voltages 364 of FIG. 3C) that indicates a likelihood that the hard bit values are correct. If a ratio of ones and zeros is very large or very small for the hard bit values, then the data may have a larger number of errors than a decoder can correct, and using an abort circuit 602 to stop the read operation may save time that would be spent on the soft read, as well as time and power to transmit and attempt to decode the data.

In a further embodiment, the adjustment circuit 506 may use the abort circuit 602 to stop one or more additional read operations subsequent to the aborted read operation. For example, as depicted in FIG. 4, a read command from a device controller 126 (for data of a transfer size 404) may correspond to a plurality of internal read operations at a smaller internal read size 402. The abort circuit 602 may stop one of the internal read operations, and subsequent internal read operations for servicing the read command. In certain embodiments, using an abort circuit 602 to stop a series of read operations may avoid further attempts to read from a highly erroneous or defective region of non-volatile storage.

In another embodiment dynamically modifying a read operation may include changing one or more read parameters during the read operation, prior to transferring the data to a device controller 126 external to a die. In a certain embodiment, the adjustment circuit 506 uses the change circuit 604 to change one or more read parameters. Although the disclosed embodiments of dynamically modifying a read operation are primarily discussed as occurring prior to transferring data to a device controller 126 (e.g., occurring substantially autonomously within an integrated circuit die), in other embodiments, the adjustment circuit 506 may be configured to change one or more read parameters after a read operation, after transferring data to the device controller 126, or the like, and may use the changed and/or adjusted one or more read parameters in a subsequent read operation.

A read parameter, as used herein, may refer to any value or factor for controlling a read operation. In various embodiments, a parameter for a read operation may be a default parameter, a parameter sent with a read command, a parameter set in a register or memory for a non-volatile memory element 123 or die, or the like. In various embodiments, read parameters may include values of read thresholds (e.g., read thresholds 302 in FIG. 3A), a bit for controlling whether a read operation includes a soft read for determining reliability of data values, or the like.

In one embodiment, the change circuit 604 may change a read parameter by changing one or more read thresholds. For example, if the threshold circuit 504 determines that a monitored balance between zeros and ones, or among states, violates a threshold, the change circuit 604 may change one or more of the read thresholds that define the boundaries between states, thus adjusting the monitored balance. In one embodiment, the threshold circuit 504 may determine that a read statistic violates a threshold after sensing at one of the read thresholds, and the change circuit 604 may change the other read thresholds, for at least the rest of the read operation. In another embodiment, the change circuit 604 may change the read thresholds and restart the read operation to use the changed read thresholds.

In a certain embodiment, the change circuit 604 may change a read parameter by changing whether the read operation includes obtaining soft bits indicating a data reliability. For example, if a monitored balance between ones and zeros violates a threshold, errors may be likely, but a decoder may be more likely to successfully decode the data if a change circuit 604 changes read parameters to obtain soft bits. In one embodiment, the change circuit 604 may temporarily change one or more read parameters for the current read operation (e.g., for the remainder of the read operation, or if the read operation is restarted). In a further embodiment, the change circuit 604 may change one or more read parameters so that the read parameters remain changed for one or more subsequent read operations.

In some embodiments, the threshold circuit 504 may compare a read statistic to multiple thresholds, and the adjustment circuit 506 may use the abort circuit 602 to stop a read operation or the change circuit 604 to change one or more read parameters depending on which thresholds the read statistic satisfies, or fails to satisfy. For example, in one embodiment, a read statistic may fail to satisfy a first threshold, indicating that the read statistic is out of an expected range, but may satisfy a second threshold, indicating that changing read parameters may make the data correctable (e.g., an error rate is likely to be within a rate that an ECC decoder can correct). In a further embodiment, the adjustment circuit 506 may dynamically modify the read operation using the change circuit 604 based on the read statistic satisfying the second threshold. In another embodiment, however, a read statistic may fail to satisfy both thresholds, indicating that the data is not likely to be correctable even with changed parameters, and the adjustment circuit 506 may use the abort circuit 602 to stop the read operation dynamically (e.g., during or within the read operation).

In various embodiments, an abort circuit 602 stopping a read operation without transferring data to a device controller 126 external to a die, or a change circuit 604 changing read parameters prior to transferring data to a device controller 126 external to a die, may conserve decoder time and power by fixing read data (or determining that the data is uncorrectable) before the data gets to a decoder. Additionally, an abort circuit 602 stopping a read operation without transferring data to a device controller 126, or a change circuit 604 changing read parameters prior to transferring data to a device controller 126 may conserve resources of a shared bus.

The status circuit 606, in one embodiment, is configured to communicate a status for the read operation to a device controller 126. In various embodiments, a status for a read operation may include any information about the state or condition of the read operation or of the data. In various embodiments, the status circuit 606 may communicate a status by sending status information with the read data, sending status information before or after the read data, sending status information in place of the read data (e.g., for an aborted read operation), sending status information separately from the read data, making status information available in a location the device controller 126 can read, or the like.

In a certain embodiment, a status communicated by the status circuit 606 may include an indication that a read operation has been stopped, an error location, and/or an indication that one or more read parameters have been changed. For example, in one embodiment, the abort circuit 602 may stop a read operation, and the status circuit 606 may communicate that the read operation has been stopped. In a further embodiment, the status circuit 606 may send an uncorrectable ECC (UECC) error code to the device controller 126. In a certain embodiment, the status circuit 606 may further indicate the location where an error has occurred. In one embodiment, where internal read operations are smaller than a data transfer size (e.g., as depicted in FIG. 4) a status circuit 606 may indicate where an error has occurred at the same granularity as the internal read operations. By contrast, a device controller 126 may only be able to determine where errors are located at the same granularity as the transfer size. In a further embodiment, the change circuit 604 may change one or more read parameters, and the status circuit 606 may communicate that the parameters have changed by sending the new parameters to the device controller 126, sending an indication that the parameters have changed, making the new parameters available for the device controller 126 to poll, or the like.

In one embodiment, the status circuit 606 may be configured to communicate a status in response to a check status command from the device controller 126. For example, a “check status” command that returns a “ready” status when data of a read operation is ready to be transferred to the device controller 126, and a “busy” status when the operation is ongoing, may be extended to return a “modified” status when a read operation has been dynamically modified based on one or more read statistics. In a further embodiment, a “modified” status may include additional fields for information about how the read operation was modified.

In another embodiment, the status circuit 606 may be configured to initiate a signal for communicating the status without being polled by the device controller 126. For example, if the abort circuit 602 aborts a read operation the status circuit 606 may send a “stopped” status without waiting to be polled by the device controller 126. In another embodiment, if the change circuit 604 changes one or more read parameters, the status circuit 606 may initiate a signal informing the device controller 126 of a latency change for the modified operation, so that the device controller 126 waits a further latency time to allow the modified read operation to complete before attempting to retrieve the data.

In a certain embodiment, the status circuit 606 is configured to communicate the status in response to a data transfer command from the device controller 126. For example, in one embodiment, a data transfer interface may be extended so that a command to transfer the data returns the data if a read operation completed normally, returns the data plus status information if the change circuit 604 changed one or more read parameters, and returns status information without data if the read operation was aborted by the abort circuit 602. Various further types of statuses and ways of communicating a status will be clear in view of this disclosure.

FIG. 7 is a schematic flow chart diagram illustrating one embodiment of a method 700 for a dynamic read operation based on read statistics. The method 700 begins, and a dynamic read component 150 initiates 702 a read operation for data of a non-volatile memory element 123. In certain embodiments, the data is stored subject to a data transformation that balances bit values for the data. A statistics circuit 502 tracks 704 an ongoing balance between bit values for the data during the read operation. An adjustment circuit 506 dynamically adjusts 706 the read operation based on the tracked ongoing balance, and the method 700 ends

FIG. 8 is a schematic flow chart diagram illustrating a further embodiment of a method 800 for a dynamic read operation based on read statistics. The method 800 begins, and a dynamic read component 150 initiates 802 a read operation for data of a non-volatile memory element 123. A statistics circuit 502 monitors 804 one or more read statistics. A threshold circuit 504 determines 806 whether the one or more read statistics satisfy a threshold. If the one or more read statistics satisfy the threshold, the statistics circuit 502 continues to monitor 804 one or more read statistics, and the method 800 continues during the remainder of the read operation. If the one or more read statistics fail to satisfy the threshold, an adjustment circuit 506 stops or changes 808 the read operation. A status circuit 606 communicates 810 the status of the read operation to a device controller 156. If the read operation was changed rather than stopped, the statistics circuit 502 continues to monitor 804 one or more read statistics, and the method 800 continues during the remainder of the read operation.

A means for monitoring one or more read statistics, in various embodiments, may include a statistics circuit 502, a dynamic read component 150, sense blocks, read/write circuits, an on-die controller, a state machine, registers or memory, logic hardware for calculating the statistics, other logic hardware, and/or other executable code stored on a computer readable storage medium. Other embodiments may include similar or equivalent means for monitoring read statistics.

A means for comparing one or more read statistics to one or more expected read statistics, in various embodiments, may include a threshold circuit 504, a dynamic read component 150, an on-die controller, a state machine, registers or memory, logic hardware for comparing the statistics, other logic hardware, and/or other executable code stored on a computer readable storage medium. Other embodiments may include similar or equivalent means for comparing read statistics to expected read statistics.

A means for dynamically updating a read operation, in various embodiments, may include an adjustment circuit 506, an abort circuit 602, a change circuit 604, a dynamic read component 150, an on-die controller, a state machine, registers or memory, other logic hardware, and/or other executable code stored on a computer readable storage medium. Other embodiments may include similar or equivalent means for dynamically updating a read operation.

A means for communicating a status for a read operation to a device controller, in various embodiments, may include a status circuit 606, a dynamic read component 150, an on-die controller, a state machine, registers or memory, a bus, other logic hardware, and/or other executable code stored on a computer readable storage medium. Other embodiments may include similar or equivalent means for communicating a status.

Alternative Embodiments

In some embodiments, dynamic read component 150 may be positioned in the device controller 126 rather than non-volatile memory (NVM) 123 as shown in FIG. 1. FIG. 9 is a conceptual block diagram 900 showing an application-specific integrated circuit (ASIC) 902 positioned in device controller 126 and incorporating at least some of the features of the dynamic read component 150 of FIG. 1, according to at least one embodiment of the invention.

The ASIC 902 may be communicatively coupled to one or more NVM (also referenced in FIG. 9, and referred to herein as NAND memory 123) via controller-NAND bus 127, similar to FIG. 1. By repositioning the dynamic read component 150 and incorporating the functionality of the dynamic read component 150 in the device controller 126, certain advantages can be realized. For example, existing hardware in the device controller 126 may be leveraged to compute the read statistics (e.g., counting the dynamic mis-compare (DMC count or DMC value), also referred to herein as the balance of zeros and ones). Such functionality will allow predicting decode failures in advance. Such functionality will also allow for alerts to be transmitted to the firmware if there is any chance to correct the data with new cell, voltage and distribution (CVD) shifts (e.g., adjusted bit thresholds in a cell) or forego exception handling all together to mitigate performance issues when trying to perform full exception handling on data that cannot be recovered. In another example, by repositioning the functionality of the dynamic read component 150 in the device controller 126, it can enable detecting failures not only related to NAND issues but also controller-NAND bus 127 issues as well. Examples of data issues on the controller-NAND bus 127 may include data dropping and reduced voltage supply that can lead to interrupted data transfer that affect the data values of the cells.

The ASIC 902 may include a segmented low-density parity check (sLDPC) module 904 (also referred to herein as “sLDPC core”). The sLDPC module 904 may be configured to perform data encoding and decoding (e.g., parity checks). The sLDPC module 904 may be configured to determine whether data decoding is feasible by analyzing the parity checks and calculating a syndrome weighting. The syndrome weighting as used herein may refer to the number of decode equations on the data that fail during the decode process. The sLDPC module 904 may be configured to perform dynamic read on portions of NAND memory 123 before decoding the data from NAND memory 123. Based on the results of the dynamic read function, the sLDPC module 904 may forego decoding (and syndrome weighting calculations) and instead opt for further error code correction (ECC) analysis as described herein. The sLDPC module 904 may allow for the predication of decode failure and notify the firmware if there is any possibility to correct the data with new CVD shifts in the threshold or alternatively whether to skip exception handling altogether.

ASIC 902 may include FIM module 906 (also referred to herein as “FIM core”). The FIM core 906 may read non-decoded data from NAND memory 123 e.g., after a scrambling/whitening event. The FIM module 906 may also calculate a read statistic, such as a DMC count. In some embodiments, the DMC count represents an even distribution (i.e., 50/50 split) between 0's and l's (or any of the states in the cell) in the data. To the extent that the DMC count deviates too far from the expected value, certain ECC or even uncorrectable ECC (UECC) functions are perform as described herein. The FIM module 906 may be coupled to the sLDPC module 904 via FIM-sLDPC line 909. The FIM module 906 may transfer the DMC count to the sLDPC module 904 for further processing.

The FIM module 906 may transfer the data read from NAND memory 123 to sLDPC module 904. In some embodiments, ASIC 902 may include data staging buffer 908 to assist with the data transfer. The data staging buffer 908 may receive data from the FIM module 906 via line 905 for staging before transfer to the sLDPC module 902 via line 907.

sLDPC module 904 may include a DMC count placeholder register 910. sLDPC module 904 may be configured to store the DMC count received form the FIM module 906 in the DMC count placeholder register 910.

sLDPC module 904 may include a decoding prediction result register 914. The decoding prediction result register 914 may be configured to store the parameters and conditional instructions to perform based on the DMC count. For example, in some embodiments, the decoding prediction result register 914 may store instructions to perform data decoding if the DMC count is approximately 50% of the total count. In another example, in some embodiments, the decoding prediction result register 914 may store instructions to perform dynamic threshold adjustment (or recalibrating read thresholds) with exception handling if the DMC count deviates slightly from 50% of the total count. In another example, in some embodiments, the decoding prediction result register 914 may store instructions to forego decoding and error code correction and instead flag the data as UECC if the DMC count deviates substantially from 50% of the total count.

sLDPC module 904 may include a DMC thresholds register 912. The configurable DMC thresholds register 912 may be configured to store the thresholds for determining when a DMC count is approximately 50% of the total bit count, when the DMC count is slightly deviated from 50% of the total count and when the DMC count is substantially deviated from 50% of the total count. For example, in some embodiments, approximately 50% of the total bit count is a value in the range of 45-55%. In some embodiments, a slight deviation from 50% is a value in the range of 40-60% but outside of the range of 45-55% of the total bit count. In some embodiments, a significant deviation is a value outside of the range of 40-60% of the total bit count. While the preceding example describes a thresholds register 912 storing thresholds that deviate from 50%, in other embodiments, other percentages of total bit count may be used (e.g., 45% or 55%). In these other embodiments, the thresholds may also be adjusted depending on the degree of deviation (e.g., slightly deviated or substantially deviated).

In some embodiments, the DMC thresholds at the DMC thresholds register 912 may be configurable. For example, the thresholds can be predetermined and configured by an operator in advance of the dynamic read. In another example, the sLDPC module 904 may adjust the thresholds via machine learning resulting in the sLDPC dynamically adjusting the DMC thresholds based on prior results. In these embodiments, the firmware decides if the DMC thresholds should be configured for the various scenarios discussed above.

ASIC 902 may include an interrupt controller 916. The interrupt controller 916 may be coupled to sLDPC module 904 via line 915. The interrupt controller 916 may be configured to alert the firmware when a sLDPC decode operation has failed. In response, the interrupt controller 916 may route the firmware to an interrupt service routine to handle the failed decode operation, which may include performing thresholds, discarding the read operation entirely, or performing other adjustments, as described herein

ASIC 902 may include firmware exception handling module 918. The firmware exception handling module 918 may be coupled to interrupt controller module 916 via line 917. The firmware exception handling module 918 may be configured to readjust thresholds and perform subsequent dynamic reads of the NAND memory 123 to determine suitable bit delineation thresholds for cells the NAND memory 123. If the firmware exception handling module 918 is unable to determine suitable bit delineation thresholds for the NAND memory 123, the firmware exception handling module 918 may indicate that the data is undecodable and flag the data as UECC.

At least some functionality of the ASIC 902, and in some embodiments more specifically the sLDPC module 904 (each of which may also referred to herein as a memory controller) may be shown in FIGS. 10-12 and described in further detail below. FIGS. 10-12 illustrate flowchart representations of methods for DMC ECC in accordance with some embodiments.

For example, FIG. 10 shows a method 1000 for DMC ECC using recalibrated thresholds in certain scenarios, in accordance with some embodiments.

In some embodiments, the method 1000 includes determining (1002) whether a DMC count is below a first threshold. In some embodiments, the first threshold is a value of approximately 50% or in the range of 45-55% of the total count. In response to a determination that the DMC count is below a first threshold, the method 1000 includes decoding the data from the NAND memory 123.

In some embodiments, the method 1000 includes determining (1004) whether the DMC count is above a first threshold and below a second threshold. In some embodiments, a second threshold is a value greater than the first threshold. In some embodiments, the second threshold in the range of 40-60% but outside of the range of 45-55% of the total bit count. In response to a determination that the DMC count is above a first threshold and below a second threshold, the method 1000 includes recalibrating the read thresholds, skip syndrome weight evaluation. The method 1000 may also include performing a subsequent read operation on the data from the NAND memory 123. In some embodiments, recalibration is performed by firmware exception handling module 918.

In some embodiments, the method 1000 includes determining (1006) whether the DMC count is above the first and second thresholds. In response to a determination that the DMC count is above the first and second thresholds, the method 1000 includes predicting that there is a failure of the decode process, i.e. UECC, and thus foregoing or bypassing the ECC completely.

FIG. 11 shows a method 1100 for DMC ECC using data block header information, in accordance with some embodiments.

In some embodiments, the method 1100 includes performing (1102) de-interleaving of the data from the NAND memory 123. De-interleaving may be performed to uncover the physical order of the interleaved data. For example, inside NAND memory 123, the cells may be interleaved according to latches inside the NAND memory 123. For instance, the cells ordered from 0 to 10, may be connected as follows: cell 0, cell 2, cell 1, cell 4, cell 3, cell 6 . . . and so on. In such an interleaved configuration, the DMC distribution will not necessarily indicate the specific location of which sets of data are set to ‘0’ and which sets of data are set to ‘1’. By performing the de-interleaving operation, one can determine where exactly which cells are in which physical location inside the NAND memory 123. By knowing the exact physical locations, the ASIC 902 may be able to detect physical defects in the NAND memory 123.

In some embodiments, the method 1100 includes portioning the NAND memory 123 into data portions (e.g., chunks) and calculating (1104) a DMC count for each data portion.

In some embodiments, the method 1100 may include determining (1106) whether the DMC count deviates significantly from a 50% of the total bit count in a data portion. In response to a determination that the DMC count deviates significantly form a 50% of the total bit count, the method 1100 include identifying the data portion as a possible physical defect and forwarding the information to the firmware exception handling module 918 for aiding in further ECC processing of the remainder of the data portions for the NAND memory 123. By identifying physical defects in portions of the data of NAND memory 123, the ASIC 902 can potentially determine that other cells in other data portions may have problems because the cells are all connected so if you see one of the cells in a portion or block is problematic, it could affect cells in other portion or block.

FIG. 12 shows a method 1200 for DMC ECC using data block header information, in accordance with some embodiments. In some embodiments, the method 1200 includes reading (1202) from a header of a data block (e.g., an SLC block as shown in FIG. 11) and extracting the expected DMC count. This header information may be used as a predictor for changing the read threshold direction. In some embodiments, the data block header is stored as additional metadata as part of a logical to physical address mapping table. The expected DMC count associated with the corresponding data block may be stored in the data block header. In response to receiving a read request for a specific data block, the expected DMC count may be extracted in association with the translation to the physical addressed as referenced in the logical to physical address mapping table. After reading the data, the actual DMC count may be compared to the expected DMC count.

In some embodiments, the method 1200 includes calculating (1204) the DMC count (e.g., at FIM module 906). The method 1200 further includes comparing the calculated DMC count to the expected DMC count.

In some embodiments, the method 1200 includes determining (1206) whether the calculated DMC is larger than the expected DMC. In response to a determination that the calculated DMC is larger than the expected DMC, the method 1200 includes shifting the read threshold in a certain direction to correct for the discrepancy. For example, if the data block is an SLC data block, then the Erase state is considered as ‘1’ and the programmed state is considered as ‘0’. If the calculated DMC count is smaller than the expected DMC count, then the read threshold is reduced in order to increase the number of zeros counted during a read operation. If the calculated DMC count is larger than the expected DMC count, then the read threshold is increased in order to reduce the number of zeros counted during a read operation. In some embodiments, the difference (DIFF) between the actual DMC count and the expected DMC count may be calculated. Then, the DIFF and a look-up-table may be used to determine how much and where the read threshold should be shifted. The sign of the DIFF may indicate the direction of the shift in the read threshold. The magnitude of the DIFF may indicate the size of the shift of the read threshold. For example, if the DIFF is a small value, the shift in the read threshold will be small and if the DIFF is a large value, then the shift in the read threshold will be large.

In some embodiments, the calculations of the DMC count may be used to verify shaped data statistics. The shaped data statistics can be verified since the data ratios are known and can be validated. The term “shaped data statistics” as used herein may refer to data (or characteristics about the data) where the expected DMC count is not 50%. For example, for shaped data, where a high portion of the data is ‘1’ for example (which may be good for endurance purposes as there have been less write operations), the expected DMC value can be 20%. In these instances, the DMC value can be used as an indication of whether the specific data is shaped or not (more ones than zeros or more zeros than ones). This information can be useful for decoding. For example, the information can be used to alter some of the decoder parameters, such as to take into account that the probability of a bit to be ‘1’ is much higher than the probability of the bit to be ‘0’ when determining when and how to alter any decoder parameters.

FIG. 13 illustrates a flowchart representation of a method 1300 for DMC ECC in accordance with some embodiments. In some embodiments, the method 1300 is performed at a controller for a non-volatile memory element, the controller being coupled to the non-volatile memory via a memory bus. For example, in some embodiments, ASIC 902 is the controller. In some embodiments, the non-volatile memory is NAND memory 123. In some embodiments, the memory bus is ASIC-NAND bus line 127.

In some embodiments, the method 1300 includes initiating (1302) a read operation for data of the non-volatile memory element, the data stored subject to a data transformation that balances ones and zeros for the data.

In some embodiments, the method 1300 includes determining (1304) whether an ongoing balance between ones and zeroes for the data during the read operation meets exception criteria.

In some embodiments, the method 1300 includes in response to a determination that the ongoing balance between ones and zeroes for the data during the read operation does not meet exception criteria: decoding (1306) data of the non-volatile memory element. In some embodiments, the exception criteria include a criterion that is met when the tracked ongoing balance does not exceed a first threshold. An example of such criterion is described with respect to FIG. 10.

In some embodiments, the method 1300 includes in response to a determination that the ongoing balance between ones and zeroes for the data during the read operation meets exception criteria: performing (1308) at least one of: dynamically adjusting the read operation based on the tracked ongoing balance, and aborting decoding on the non-volatile memory element without performing error code correction and without transferring the data from the non-volatile memory to a host controller. In some embodiments, dynamically adjusting the read operation comprises changing one or more read parameters during the read operation, prior to transferring the data to a host controller. In some embodiments, changing one or more read parameters comprises one or more of: changing one or more read thresholds of the cells in the NAND memory (e.g., NAND memory 123); and obtaining soft bits indicating a reliability of the data. In some embodiments, the read parameters are stored in decoding prediction result register 914. In some embodiments, the read thresholds are stored in configurable DMC threshold register 912.

In some embodiments, the exception criteria are not met when the tracked ongoing balance exceeds the first threshold but is less than a second threshold. In some embodiments, in response to a determination that that the ongoing balance between ones and zeroes for the data during the read operation exceeds the first threshold but is less than a second threshold: dynamically adjusting the read operation based on the tracked ongoing balance. An example of such criterion is described with respect to FIG. 10.

In some embodiments, the exception criteria are not met when the tracked ongoing balance exceeds the first threshold but is less than the second threshold. In some embodiments, in response to a determination that that the ongoing balance between ones and zeroes for the data during the read operation exceeds the first threshold and the second threshold: aborting decoding on the non-volatile memory element without performing error code correction and without transferring the data from the non-volatile memory to a host controller. An example of such criterion is described with respect to FIG. 10.

In some embodiments, before determining an ongoing balance between ones and zeroes for the data during the read operation, de-interleaving the data into respective data portions having a known physical order; for each of the respective data portions, performing the determining step at step 1304. In some embodiments, in response to a determination that ongoing balance between ones and zeroes for the respective data portion meets exception criteria: identifying that the respective data portion has a possible physical defect and transmitting possible physical defect information for the respective data portion to the device controller. An example of such criterion is described with respect to FIG. 11.

In some embodiments, determining whether an ongoing balance between ones and zeroes for the data during the read operation meets exception criteria includes comparing the ongoing balance to one or more data statistics to verify and validate the shaped data.

In some embodiments, reading a block data header associated with the data indicated in the read operation to determine an expected balance between ones and zeroes for the data during the read operation. In some embodiments, determining whether an ongoing balance between ones and zeroes for the data during the read operation meets exception criteria includes comparing the ongoing balance to the expected balance. In some embodiments, the exception criteria include a criterion that is met when the tracked ongoing balance is greater than the expected balance. In some embodiments, in response to a determination that the tracked ongoing balance is greater than the expected balance: dynamically adjusting the read operation based on the tracked ongoing balance. An example of such criterion is described with respect to FIG. 12.

The present disclosure may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the disclosure is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope. 

What is claimed is:
 1. A method comprising: at a controller for a non-volatile memory element, the controller being coupled to the non-volatile memory via a memory bus: initiating a read operation for data of the non-volatile memory element, the data stored subject to a data transformation that balances ones and zeros for the data. determining whether an ongoing balance between ones and zeroes for the data during the read operation meets exception criteria; in response to a determination that the ongoing balance between ones and zeroes for the data during the read operation does not meet exception criteria: decoding data of the non-volatile memory element; in response to a determination that the ongoing balance between ones and zeroes for the data during the read operation meets exception criteria: performing at least one of: dynamically adjusting the read operation based on the tracked ongoing balance, and aborting decoding on the non-volatile memory element without performing error code correction and without transferring the data from the non-volatile memory to a host controller.
 2. The method of claim 1, wherein the exception criteria include a criterion that is met when the tracked ongoing balance does not exceed a first threshold.
 3. The method of claim 2, wherein the exception criteria are not met when the tracked ongoing balance exceeds the first threshold but is less than a second threshold; and further comprising: in response to a determination that that the ongoing balance between ones and zeroes for the data during the read operation exceeds the first threshold but is less than a second threshold: dynamically adjusting the read operation based on the tracked ongoing balance.
 4. The method of claim 3, wherein the exception criteria is not met when the tracked ongoing balance exceeds the first threshold but is less than the second threshold; and further comprising: in response to a determination that that the ongoing balance between ones and zeroes for the data during the read operation exceeds the first threshold and the second threshold: aborting decoding on the non-volatile memory element without performing error code correction and without transferring the data from the non-volatile memory to a host controller
 5. The method of claim 1, wherein dynamically adjusting the read operation comprises changing one or more read parameters during the read operation, prior to transferring the data to a host controller.
 6. The method of claim 5, wherein changing one or more read parameters comprises one or more of: changing one or more read thresholds; and obtaining soft bits indicating a reliability of the data.
 7. The method of claim 1, further comprising: at the controller: before determining an ongoing balance between ones and zeroes for the data during the read operation, de-interleaving the data into respective data portions having a known physical order for each of the respective data portions, performing the determining step of claim 1, wherein in response to a determination that ongoing balance between ones and zeroes for the respective data portion meets exception criteria: identifying that the respective data portion has a possible physical defect and transmitting possible physical defect information for the respective data portion to the device controller.
 8. The method of claim 1, wherein determining whether an ongoing balance between ones and zeroes for the data during the read operation meets exception criteria includes comparing the ongoing balance to one or more data statistics to verify and validate the shaped data.
 9. The method of claim 1, further comprising: at the controller: reading a block data header associated with the data indicated in the read operation to determine an expected balance between ones and zeroes for the data during the read operation; wherein determining whether an ongoing balance between ones and zeroes for the data during the read operation meets exception criteria includes comparing the ongoing balance to the expected balance, and wherein the exception criteria includes a criterion that is met when the tracked ongoing balance is greater than the expected balance, and wherein in response to a determination that the tracked ongoing balance is greater than the expected balance: dynamically adjusting the read operation based on the tracked ongoing balance.
 10. A system comprising: a non-volatile memory element; a memory bus; and a controller for the non-volatile memory element, the controller being coupled to the non-volatile memory via the memory bus, the controller configured to perform the steps of: initiating a read operation for data of the non-volatile memory element, the data stored subject to a data transformation that balances ones and zeros for the data. determining whether an ongoing balance between ones and zeroes for the data during the read operation meets exception criteria; in response to a determination that the ongoing balance between ones and zeroes for the data during the read operation does not meet exception criteria: decoding data of the non-volatile memory element; in response to a determination that the ongoing balance between ones and zeroes for the data during the read operation meets exception criteria: performing at least one of: dynamically adjusting the read operation based on the tracked ongoing balance, and aborting decoding on the non-volatile memory element without performing error code correction and without transferring the data from the non-volatile memory to a host controller.
 11. The system of claim 10, wherein the exception criteria include a criterion that is met when the tracked ongoing balance does not exceed a first threshold.
 12. The system of claim 11, wherein the exception criteria are not met when the tracked ongoing balance exceeds the first threshold but is less than a second threshold; and further comprising: in response to a determination that that the ongoing balance between ones and zeroes for the data during the read operation exceeds the first threshold but is less than a second threshold: dynamically adjusting the read operation based on the tracked ongoing balance.
 13. The system of claim 12, wherein the exception criteria are not met when the tracked ongoing balance exceeds the first threshold but is less than the second threshold; and further comprising: in response to a determination that that the ongoing balance between ones and zeroes for the data during the read operation exceeds the first threshold and the second threshold: aborting decoding on the non-volatile memory element without performing error code correction and without transferring the data from the non-volatile memory to a host controller
 14. The system of claim 10, wherein dynamically adjusting the read operation comprises changing one or more read parameters during the read operation, prior to transferring the data to a host controller.
 15. The system of claim 14, wherein changing one or more read parameters comprises one or more of: changing one or more read thresholds; and obtaining soft bits indicating a reliability of the data.
 16. The system of claim 10, wherein the controller is further configured to perform the steps of: before determining an ongoing balance between ones and zeroes for the data during the read operation, de-interleaving the data into respective data portions having a known physical order for each of the respective data portions, performing the determining step of claim 1, wherein in response to a determination that ongoing balance between ones and zeroes for the respective data portion meets exception criteria: identifying that the respective data portion has a possible physical defect and transmitting possible physical defect information for the respective data portion to the device controller.
 17. The system of claim 10, wherein determining whether an ongoing balance between ones and zeroes for the data during the read operation meets exception criteria includes comparing the ongoing balance to one or more data statistics to verify and validate the shaped data.
 18. The system of claim 10, wherein the controller is further configured to perform the steps of: reading a block data header associated with the data indicated in the read operation to determine an expected balance between ones and zeroes for the data during the read operation; wherein determining whether an ongoing balance between ones and zeroes for the data during the read operation meets exception criteria includes comparing the ongoing balance to the expected balance, and wherein the exception criteria include a criterion that is met when the tracked ongoing balance is greater than the expected balance, and wherein in response to a determination that the tracked ongoing balance is greater than the expected balance: dynamically adjusting the read operation based on the tracked ongoing balance. 